Association of content identifier of audio-visual data with additional data through capture infrastructure

ABSTRACT

A method of a capture infrastructure includes determining a content identifier by applying a first automatic content recognition algorithm to fingerprint data of an audio-visual data rendered on a networked media device, and associating the content identifier with additional data derived from information other than the fingerprint data.

CLAIM OF PRIORITY

This patent application is a Continuation-in-Part application and hereby incorporates the entirety of the disclosures of, and claims priority to, each of the following cases:

U.S. utility application Ser. No. 15/259,146 titled ANNOTATION OF METADATA THROUGH CAPTURE INFRASTRUCTURE (to be issued as U.S. Pat. No. 10,074,108 on Sep. 11, 2018), which is a continuation application of:

U.S. utility application Ser. No. 14/018,396 titled, ANNOTATION OF METADATA THROUGH CAPTURE INFRASTRUCTURE filed on Sep. 4, 2013 and issued as U.S. Pat. No. 9,576,473 on Feb. 21, 2017. U.S. utility application Ser. No. 14/018,396 further claims the priority to:

U.S. Provisional Patent application No. 61/118,286 filed Nov. 26, 2008 and titled DISCOVERY, ACCESS CONTROL, AND COMMUNICATION WITH NETWORKED SERVICES FROM WITHIN A SECURITY SANDBOX,

U.S. utility application Ser. No. 13/470,814 filed May 14, 2012 titled GENERATION OF A TARGETED ADVERTISEMENT IN AN UNTRUSTED SANDBOX BASED ON A PSUEDONYM and issued as U.S. Pat. No. 8,539,072 on Sep. 17, 2013,

U.S. utility application Ser. No. 12/592,377 filed Nov. 23, 2009 titled DISCOVERY, ACCESS CONTROL, AND COMMUNICATION WITH NETWORKED SERVICES FROM WITHIN A SECURITY SANDBOX and issued as U.S. Pat. No. 8,180,891 on May 15, 2012,

U.S. Provisional Patent application No. 61/584,168 filed Jan. 6, 2012 and titled CAPTURING CONTENT FOR DISPLAY ON A TELEVISION,

U.S. Provisional Patent application No. 61/696,711 filed Sep. 4, 2012 and titled SYSTEMS AND METHODS FOR RECOGNIZING CONTENT, and

U.S. Utility patent application Ser. No. 13/736,031 filed Jan. 7, 2013 titled ZERO CONFIGURATION COMMUNICATION BETWEEN A BROWSER AND A NETWORKED MEDIA DEVICE and issued as U.S. Pat. No. 9,154,942 on Oct. 6, 2015.

FIELD OF TECHNOLOGY

This disclosure relates generally to the technical field of media content distribution, and, more specifically, to a method and an apparatus of association of content identifier of audio-visual data with additional data through capture infrastructure.

BACKGROUND

A user may access a mobile communication device while watching television. An advertisement presented to the user on the mobile communication device may be independent of the content being viewed on the television. For example, the user may be watching a television show about car washes. However, advertisements displayed on the mobile device may have nothing to do with water, cars, and/or cleanliness. Similarly, advertisements displayed on the television may not appreciate a present activity of the user when accessing the mobile device. As such, an advertiser may miss key marketing opportunities to the user to deliver highly targeted and relevant advertising to the user.

SUMMARY

A method and an apparatus of association of content identifier of audio-visual data with additional data through capture infrastructure are disclosed.

In one aspect, a method of a capture infrastructure includes determining a content identifier by applying a first automatic content recognition algorithm to fingerprint data of an audio-visual data rendered on a networked media device, and associating the content identifier with additional data derived from information other than the fingerprint data.

In another aspect, a capture infrastructure includes a memory, and a processor communicatively coupled to the memory. The processor is configured to execute instructions to determine a content identifier by applying a first automatic content recognition algorithm to fingerprint data of an audio-visual data rendered on a networked media device, and to associate the content identifier with additional data derived from information other than the fingerprint data.

The methods, system, and/or apparatuses disclosed herein may be implemented in any means for achieving various aspects, and may be executed in a form of machine readable medium embodying a set of instruction that, when executed by a machine, causes the machine to perform any of the operations disclosed herein. Other features will be apparent from the accompanying drawing and from the detailed description that follows.

BRIEF DESCRIPTION OF DRAWINGS

Example embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawing, in which like references indicate similar elements and in which:

FIG. 1 is a block diagram of a system of automatic bidirectional communication between multiple devices sharing a common network, according to one embodiment.

FIG. 2 is a block diagram of a system of automatic bidirectional communication between a client device 100 and a networked device 102 using a server, according to one embodiment.

FIG. 3 is an exploded view of the security sandbox 104, according to one embodiment.

FIG. 4 is an exploded view of the pairing server 200, according to one embodiment.

FIG. 5 is an exploded view of the client device 100, according to one embodiment.

FIG. 6 is a table of example network information stored in a database 422 of a pairing server 200, according to one embodiment.

FIG. 7 is a block diagram of a method by which a security sandbox 104 can communicate with a sandbox reachable service 114 that previously operated on a shared network 202, according to one embodiment.

FIG. 8 is a schematic diagram of a private network 800 and a private network 802 communicating over the public Internet via a NAT device 804 and a NAT device 806, according to one embodiment.

Other features of the present embodiments will be apparent from the accompanying drawings and from the detailed description that follows.

DETAILED DESCRIPTION

A method and an apparatus of association of content identifier of audio-visual data with additional data through capture infrastructure are disclosed.

In one embodiment, a method of a client device 100 includes applying an automatic content recognition algorithm (e.g., in the algorithm library 107) to determine a content identifier 111 of an audio-visual data (e.g., a movie, a television show, an advertisement, etc.). The client device 100 then associates the content identifier 111 with an advertisement data 113 based on a semantic correlation between a meta-data of the advertisement (a particular advertisement of the advertisement data 113) provided by a content provider (e.g., an organization providing advertisements) and/or the content identifier 111. A capture infrastructure 105 annotates the audio-visual data with a brand name and/or a product name by comparing entries in the master database 109 with a closed captioning data of the audio-visual data and/or through an application of an optical character recognition algorithm (e.g., in the algorithm library 107) in the audio-visual data. The content identifier 111 may involve a music identification, an object identification, a facial identification, and/or a voice identification. A minimal functionality including accessing a tuner and/or a stream decoder that identifies a channel and/or a content may be found in the networked media device (e.g., the networked device 102). The networked media device (e.g., the networked device 102) may produce an audio fingerprint and/or a video fingerprint that is communicated with the capture infrastructure 105.

The capture infrastructure 105 may compare the audio fingerprint and/or the video fingerprint with a master database 109. The capture infrastructure 105 may further annotate the audio-visual data with a logo name by comparing entries in the master database 109 with a logo data of the audio-visual data identified using a logo detection algorithm (e.g., in the algorithm library 107). The capture infrastructure 105 may automatically divide the audio-visual data into a series of scenes based on a sematic grouping of actions in the audio-visual data. The audio-visual data may be analyzed in advance of a broadcast to determine content identifier 111 s associated with each commercial in the audio-visual data such that advertisements are pre-inserted into the audio-visual data prior to broadcast.

The capture infrastructure 105 may apply a time-order algorithm (e.g., in the algorithm library 107) to automatically match advertisements to the audio-visual data when a correlation pattern is identified by the capture infrastructure 105 with other audio-visual content previously analyzed. The capture infrastructure 105 may include a buffer that is saved to a persistent storage and/or for which a label is generated to facilitate identification of reoccurring sequences. A post processing operation may be automated through a post-processing algorithm (e.g., in the algorithm library 107) and/or a crowd-sourced operation using a plurality of users in which a turing test is applied to determine a veracity of an input.

A device pairing algorithm (e.g., in the algorithm library 107) may be used in which a cookie data associated with a web page visited by the user stored on a browser on the client device 100 is paired with the networked media device (e.g., the networked device 102) when the client device 100 is communicatively coupled with the networked media device (e.g., the networked device 102). A transitive public IP matching algorithm (e.g., in the algorithm library 107) may be utilized in which the client device 100 and/or the networked media device (e.g., the networked device 102) communicates each public IP address with any paired entity to the capture infrastructure 105. A tag that is unconstrained from a same-origin policy may be used to automatically load the advertisement in the browser, the tag is an image tag, a frame, a iframe, and/or a script tag.

An additional metadata including the content identifier 111 and/or the advertisement based on a video processing algorithm (e.g., in the algorithm library 107) may be referenced. The additional meta data may be a title, a description, a thumbnail, a name of an individual, and/or a historical data. The additional metadata may be determined from a browser history captured from the client device 100 based on a capture policy, and/or correlating a relevance of the browser history with the content identifier 111 and/or the advertisement.

In another embodiment, a method of a networked device includes applying an automatic content recognition algorithm (e.g., in the algorithm library 107) to determine a content identifier 111 of an audio-visual data, and associating the content identifier 111 with an advertisement data 113 based on a semantic correlation between a meta-data of the advertisement provided by a content provider and/or the content identifier 111. In this other aspect, a capture infrastructure 105 annotates the audio-visual data with a brand name and/or a product name by comparing entries in the master database 109 with a closed captioning data of the audio-visual data and/or through an application of an optical character recognition algorithm (e.g., in the algorithm library 107) in the audio-visual data.

In yet another embodiment, a system includes a networked device and/or a client device 100 to apply an automatic content recognition algorithm (e.g., in the algorithm library 107) to determine a content identifier 111 of an audio-visual data and/or to associate the content identifier 111 with an advertisement data 113 based on a semantic correlation between a meta-data of the advertisement provided by a content provider and/or the content identifier 111. The system also includes a capture infrastructure 105 to annotate the audio-visual data with a brand name and/or a product name by comparing entries in the master database 109 with a closed captioning data of the audio-visual data and/or through an application of an optical character recognition algorithm (e.g., in the algorithm library 107) in the audio-visual data.

FIG. 1 is a block diagram of a system of automatic bidirectional communication (e.g., sending and receiving information in both directions without prior configuration by a human) between multiple devices sharing a common network, according to one embodiment. FIG. 1 shows a client device 100, a networked device 102, a security sandbox 104, an executable environment 106, a processor 108, a storage 109, a memory 110, a sandboxed application 112, and a sandbox reachable service 114. The client device 100 communicates bidirectionally with the networked device 102 of FIG. 1.

According to one embodiment, a client device 100 may be a computer, a smartphone, and/or any other hardware with a program that initiates contact with a server to make use of a resource. A client device 100 may constrain an executable environment 106 in a security sandbox 104, execute a sandboxed application 112 in a security sandbox 104 using a processor 108 and a memory 110, and automatically instantiate (e.g., manifest) a connection (e.g., a complete path between two terminals over which two-way communications may be provided) between a sandboxed application 112 and a sandbox reachable service 114 of the networked device 102.

According to one embodiment, a networked device 102 may be a television, stereo, game console, another computer, and/or any other hardware connected by communications channels that allow sharing of resources and information. A networked device 102 may comprise a number of sandbox reachable applications. A networked device 102 may announce a sandbox reachable service 114 using a processor 108 and a memory 110. According to one embodiment, a processor 108 may be a central processing unit (CPU), a microprocessor, and/or any other hardware within a computer system which carries out the instructions of a program by performing the basic arithmetical, logical, and input/output operations of the system. According to one embodiment, a memory 110 may be a random access memory (RAM), a read only memory (ROM), a flash memory, and/or any other physical devices used to store programs or data for use in a digital electronic device.

The security sandbox 104, the processor 108, the storage 109, and the memory 110 each exist within the client device 100 of FIG. 1, and they communicate bidirectionally with each other. According to one embodiment, a security sandbox 104 may be an operating system on which the sandboxed application 112 is hosted, a browser application of the operating system, and/or any other mechanism for separating running programs to execute untested code and/or untrusted programs from unverified third-parties, suppliers, untrusted users, and untrusted websites. According to one embodiment, a storage 109 may be a technology consisting of computer components and recording media used to retain digital data.

The executable environment 106 exists within the security sandbox 104 of FIG. 1. According to one embodiment, an executable environment 106 may be a virtual machine, a jail, a scripting language interpreter, a scratch space on disk and memory, and/or any other tightly controlled set of resources in which to run guest programs.

The sandboxed application 112 exists within the executable environment 106 of FIG. 1. According to one embodiment, a sandboxed application 112 may be an untested code, an untrusted program (e.g., from an untrusted web page), and/or any other software that can be executed with the appropriate runtime environment of the security sandbox 104.

The sandbox reachable service 114 exists within the networked device 102 of FIG. 1. According to one embodiment, a sandbox reachable service 114 may be a smart television application, a set-top box application, an audio device application, a game console application, a computer application, and/or any other service that can be discovered and communicated with from within the sandboxed application 112. FIG. 1 may encompass constraining a sandbox reachable service 114 in a security sandbox 104 where it is described sandbox reachable service 114, according to one embodiment. A security sandbox 104 may not allow a sandbox reachable service 114 that is constrained in the security sandbox 104 to open a server socket and receive inbound connections. However, a sandbox reachable service 114 that is constrained in the security sandbox 104 may still announce and be discovered, but all communications between a client device 100 and a networked device 102 may need to traverse through a relay in a pairing server 200.

FIG. 2 is a block diagram of a system of automatic bidirectional communication between a client device 100 and a networked device 102 using a server, according to one embodiment. FIG. 2 shows a client device 100, a networked device 102, a security sandbox 104, an executable environment 106, a processor 108, a memory 110, a sandboxed application 112, a pairing server 200, a shared network 202, a Wide Area Network (WAN) 204, a devices 206, a global unique identifier (GUID) 208, an alphanumeric name 210, a private address pair 212, a sandbox reachable service 114, an identification data 216, a switch 218, a public address pair 220, and a hardware address 222.

The client device 100, the networked device 102, and the devices 206 communicate bidirectionally with each other through the switch 218 in the shared network 202. According to one embodiment, a devices 206 may be a television, a projection screen, a multimedia display, a touchscreen display, an audio device, a weather measurement device, a traffic monitoring device, a status update device, a global positioning device, a geospatial estimation device, a tracking device, a bidirectional communication device, a unicast device, a broadcast device, a multidimensional visual presentation device, and/or any other devices with a network interface. According to one embodiment, a switch 218 may be a telecommunication device (e.g., a broadcast, multicast, and/or anycast forwarding hardware) that receives a message from any device connected to it and then transmits the message only to the device for which the message was meant.

According to one embodiment, a shared network 202 may be a local area network, a multicast network, an anycast network, a multilan network, a private network (e.g., any network with a private IP space), and/or any other collection of hardware interconnected by communication channels that allow sharing of resources and information. When a sandboxed application 112 and a sandbox reachable service 114 communicate in a shared network 202 common to the client device 100 and a networked device 102 when a connection is established, a client device 100 may eliminate a communication through a centralized infrastructure (e.g., a pairing server 200 which may be used only for discovery), minimize latency in the communication session (e.g., by establishing a connection between a client device 100 and a networked device 102 rather than by relaying via a pairing server 200), and improve privacy in the communication session.

FIG. 2 may encompass establishing a shared network 202 based on a bidirectional communication that does not use a relay service where it is described a shared network 202, according to one embodiment. Multiple local area networks (LANs) may share a public IP address. A client device 100 may reside on one LAN, and a sandbox reachable service 114 may reside on another LAN. A client device 100 may discover a sandbox reachable service by matching public Internet Protocol (IP) addresses. However, a sandbox reachable service 114 that is not constrained to a security sandbox 104 may have an unconstrained view (e.g., it may have access to Media Access Control addresses, Address Resolution Protocol, and/or routing tables) of a shared network 202.

A client device 100 may attempt to communicate with a sandbox reachable service 114 (e.g., by opening a Transmission Control Protocol connection and/or by sending a User Datagram Protocol datagram) without using a relay service. A shared network 202 may be established if a connection successfully handshakes, a datagram arrives, and/or the client device 100 and the sandbox reachable service 114 otherwise communicate bidirectionally without using a relay service.

FIG. 2 may also encompass establishing a shared network 202 based on a determination that a client device 100 and a sandbox reachable service 114 reside on a same LAN where it is described a shared network 202, according to one embodiment. For example, a networked device 102 may broadcast ping (e.g., using Internet Control Message Protocol) and listen for a response from a client device 100.

FIG. 2 may further encompass establishing a shared network 202 by using an address resolution protocol (e.g., ARP) where it is described a shared network 202, according to one embodiment. A sandbox reachable service 114 may determine that a client device 100 resides on a same LAN if the IP address of the client device 100 can be resolved to a LAN address using an IP-to-LAN address resolution protocol (e.g., ARP).

The shared network 202 communicates with the pairing server 200 through the WAN 204. According to one embodiment, a pairing server 200 may be a computer hardware system dedicated to enabling communication between a sandboxed application 112 and a sandbox reachable service 114. According to one embodiment, a WAN 204 may be the Internet and/or any other telecommunications network that links across metropolitan, regional, and/or national boundaries using private and/or public transports. A networked device 102 may announce an availability of a sandbox reachable service 114 across a range of public addresses such that a sandboxed application 112 communicates with the sandbox reachable service 114 in any one of the range of the public addresses. However, a range of public addresses may be known by a pairing server 200 so that the announcement of the availability of a sandbox reachable service 114 across a range of public addresses is unnecessary.

The identification data 216 exists within the sandbox reachable service 114 of FIG. 2. According to one embodiment, an identification data 216 may be a reference information associated with an application sharing a public address with a client device 100, a networked device 102, and/or a devices 206 (e.g., to define a network in which the client device 100, the networked device 102, and/or the devices 206 reside). A client device 100 may access a pairing server 200 when processing an identification data 216 associated with a sandbox reachable service 114 sharing a public address with the client device 100. A pairing server 200 may perform a discovery lookup of any device that has announced that it shares a public address associated with the client device 100. Further, a sandbox reachable service 114 may announce itself to a pairing server 200 prior to the establishment of a communication session between a sandboxed application 112 and the sandbox reachable service 114.

The GUID 208, the alphanumeric name 210, the private address pair 212, the public address pair 220, and the hardware address 222 each exist within the identification data 216 of FIG. 2. According to one embodiment, a GUID 208 may be a 128-bit reference number used by software programs to uniquely identify the location of a data object. For example, FIG. 2 may be applicable to a GUID 208 of a sandbox reachable service 114 and/or a networked device 102 where it is described a global unique ID 208. It may be preferable to have a one-to-one mapping between a GUID 208 and a networked device 102. However, in the case when a sandbox reachable service 114 may be constrained to a security sandbox 104, the sandbox reachable service 114 may have no way of determining its own IP address and/or whether it resides on a same device with other services. In this case, every sandbox reachable service 114 on the same device may have its own GUID 208.

According to one embodiment, an alphanumeric name 210 may be a “Vizio® 36″ TV,” a “living room TV,” a “bedroom printer,” and/or any other human-friendly reference name of a networked device 102. According to one embodiment, a private address pair 212 may be a private Internet Protocol (IP) address and a port number associated with an application that sends and/or receives packets. According to one embodiment, a public address pair 220 may be a public IP address and a port number 604 associated with an application that sends and/or receives packets. According to one embodiment, a hardware address 222 may be a Media Access Control (MAC) address, a physical address, Ethernet hardware address (EHA), and/or any other unique identifier assigned to network interfaces for communications on the physical network segment.

A client device 100 may process an identification data 216 associated with a sandbox reachable service 114 sharing a public address with the client device 100 and determine a private address pair 212 of the sandbox reachable service 114 based on the identification data 216. A networked device 102 may also communicate a global unique identifier 208 and/or an alphanumeric name 210 to a pairing server 200 along with a hardware address 222 associated with the networked device 102, a public address pair 220 associated with a sandbox reachable service 114 of the networked device 102, and/or a private address pair 212 associated with the sandbox reachable service 114 of the networked device 102.

FIG. 3 is an exploded view of the security sandbox 104, according to one embodiment. FIG. 3 shows a security sandbox 104, a sandboxed application 112, a same origin policy exception 300, a web page 302, a script 304, a binary executable 306, an intermediate bytecode 308, an abstract syntax tree 310, an executable application 312, a HyperText Markup Language 5 (HTML5) application 314, a Javascript® application 316, an Adobe® Flash® application 318, an Asynchronous Javascript® and XML (AJAX) application 320, a JQuery® application 324, a Microsoft® Silverlight® application 326, a hyperlink 328, a frame 330, a script 332, an image 334, a header 336, and a form 338.

The sandboxed application 112 exists within the security sandbox 104 of FIG. 3. The web page 302, the script 304, the binary executable 306, the intermediate bytecode 308, the abstract syntax tree 310, and the executable application 312 are listed as general examples of the sandboxed application 112 of FIG. 3. According to one embodiment, a web page 302 may be a document and/or an information resource that is suitable for the World Wide Web and can be accessed through a web browser and displayed on a monitor and/or a mobile device. According to one embodiment, a script 304 may be a program written for a software environment that automates the execution of tasks which could alternatively be executed one-by-one by a human operator.

According to one embodiment, a binary executable 306 may be a binary file that may include a program in machine language which is ready to be run. According to one embodiment, an intermediate bytecode 308 may be a programming language implementation of instruction set designed for efficient execution by a software interpreter. According to one embodiment, an abstract syntax tree 310 may be a tree representation of the abstract syntactic structure of source code written in a programming language. According to one embodiment, an executable application 312 may be a file that causes a computer to perform indicated tasks according to encoded instructions.

The HTML5 application 314, the Javascript® application 316, the Adobe® Flash® application 318, the Microsoft® Silverlight® application 326, the JQuery® application 324, and the AJAX application 320 are listed as specific examples of the general examples of FIG. 3. According to one embodiment, a HTML5 application 314 may be a program written in the fifth revision of the hypertext markup language standard for structuring and presenting content for the World Wide Web. According to one embodiment, a Javascript® application 316 may be a program written in a scripting language commonly implemented as part of a web browser in order to create enhanced user interfaces and dynamic websites. According to one embodiment, an Adobe® Flash® application 318 may be a program written for a multimedia and software platform used for authoring of vector graphics, animation, games and Rich Internet Applications (RIAs) which can be viewed, played, and executed in Adobe® Flash® Player.

According to one embodiment, an AJAX application 320 may be a program using a XMLHttpRequest method, a program using a Msxml2.XMLHTTP method, a program using a Microsoft.XMLHTTP method, and/or any other web program that can send data to and retrieve data from a server in the background without interfering with the display and behavior of the existing page. According to one embodiment, a JQuery® application 324 may be a program written using a multi-browser collection of pre-written Javascript® designed to simply the client-side scripting of HTML. According to one embodiment, a Microsoft® Silverlight® application 326 may be a program written in a framework for writing and running RIAs with features and purposes similar to those of Adobe® Flash®.

The same origin policy exception 300 extends horizontally below the security sandbox 104 of FIG. 3. According to one embodiment, a same origin policy exception 300 may be a cross-domain scripting technique, a cross-site scripting technique, a document.domain property, a Cross-Origin Resource Sharing (CORS), a cross-document messaging, a technique for relaxing a policy preventing access to methods and properties across pages on different sites, and/or an access control algorithm governing a policy through which a secondary authentication is required when establishing a communication between the sandboxed application 112 and the networked device 102.

A client device 100 may establish a communication session between a sandboxed application 112 and a sandbox reachable service 114 using a cross-site scripting technique of a security sandbox 104. A client device 100 may also append a header 336 of a hypertext transfer protocol to permit a networked device 102 to communicate with a sandboxed application 112 as a permitted origin domain through a Cross-origin resource sharing (CORS) algorithm. Further, a client device 100 may utilize a same origin policy exception 300 through a use of a hyperlink 328, a form 338, a script 332, a frame 330, a header 336, and/or an image 334 when establishing the connection between a sandboxed application 112 and a sandbox reachable service 114.

For example, FIG. 3 may encompass a HTML5 cross-domain scripting using postMessage where it is described HTML5 application 314. With postMessage, a calling window may call any other window in a hierarchy including those in other domains. A receiving window may set up a message listener to receive said message and can return results by posting a result message back to a calling frame. Assuming a web page residing at http://example.com/index.html:

<iframe src=”http://bar.com” id=”iframe”></iframe> <form id=”form”>  <input type=”text″ id=″msg″ value=″Message to send″/>  <input type=″submit″/> </form> <script> window.onload = function( ){ var win = document.getElementById(″iframe″).contentWindow; document.getElementById(″form″).onsubmit = function(e){ win.postMessage( document.getElementById(″msg″).value ); e.preventDefault( ); }; }; </script>

An iframe may load the following HTML from bar.com:

<b>This iframe is located on bar.com</b> <div id=“test”>Send me a message!</div> <script> document.addEventListener(“message”, function(e){ document.getElementById(“test”).textContent = e.domain + “ said: ” + e.data; }, false); </script>

When a user 820 (e.g., a human agent who uses a service) clicks on the submit button, a message may be posted to the frame read from bar.com which changes “Send me a message!” to http://bar.com said: Message to send.

The hyperlink 328, the frame 330, the script 332, the image 334, the header 336, and the form 338 comprise aspects of the same origin policy exception 300 of FIG. 3. According to one embodiment, a hyperlink 328 may be a reference to data that a reader can directly follow and/or that is followed automatically. FIG. 3 may also be applicable to a hyperlink send message interface (e.g., a mechanism by which a sandboxed application 112 sends a message to a pairing server 200) where it is described a hyperlink 328 using an <A> tag to send a message to a pairing server 200 comprised of a discovery service and a relay service. The <A> tag may link to pages that are not in a same domain as a web page being viewed in a browser. As such a link may point to the pairing server 200 and arguments to be passed in a message may be encoded as key-value pairs in a uniform resource identifier (URI) query string. For example,

<A HREF=http://pairing_server.com/f?a=10&b=bar>call f</A>

A sandboxed application 112 may announce to the pairing server 200. At a later time, a user 820 may visit example.com and view index.html. When the user 820 clicks on a “call f” hyperlink, a HTTP request may be sent to the pairing server 200. “f” may refer to a path to some arbitrary function and key-value pairs a=10 and/or b=bar may be arguments to that function. The pairing server 200 may receive an HTTP GET like this request generated using Google Chrome™:

GET /f?a=10&b=bar HTTP/1.1 Host: pairing_server.com Connection: keep-alive Referer: http://example.dom/index.html Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/pn g,*/*;q=0.5 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

The URI may not indicate to which service a message is intended. This may be interpreted by the pairing server 200 as a private broadcast meaning that a message passed via a message query interface (e.g., a mechanism to communicate a message from a pairing server 200 to a sandbox reachable service 114) is passed to all sandbox reachable services in a shared network 202. In this case, a response HTML may simply be a new web page that may include a confirmation dialog and/or a notification that a message has been sent.

According to one embodiment, a frame 330 may be a frameset, an inline frame, and/or any display of web pages and/or media elements within the same browser window. According to one embodiment, a script 332 may be a HTML tag used to define a program that may accompany an HTML document and/or be directly embedded in it. FIG. 3 may encompass a SCRIPT tag where it is described a script 332 used to contact the pairing server 200. For example, a server may deliver an http://example.com/index.html that may include a cross-site <script> tag as follows:

<html>...<head> <script type=″text/Javascript″> function lookup_cb(d) { var services = d[″services″]; var slen = services.length; var s, len; s= ″<ul>″; for ( var i = 0; i < slen; ++i ) s = s + ″<li>″ + services[i].name + ″</li>″; s = s + ″</ul>″; document.getElementById(″services″).innerHTML=s; } </script></head><body> ... <div id=”services”></div> ... <script id=″external_script″ type=″text/Javascript″></script> <script> document.getElementById(″external_script″).src = ″http://pairing_server.com/fling/lookup?callback=lookup_cb″; </script></body></html>

In the example above, Javascript® may replace a source of a <script> with id “external script” with a script downloaded from the pairing server 200. A call being made to a sandbox reachable service 114 may be embedded in a call to “lookup” with a single argument “callback=lookup_cb.” The pairing server 200 may return a script that may include a result, e.g.,

lookup_cb({ “services”: [...], “yourip”: “69.106.59.218”, “version”: “1.0”, “interval”: 900 })

The result above may include a list of “services” discovered in a user's (e.g., the user of the client device 100) shared network 202. The result may be encapsulated inside a call to lookup_cb which was a callback passed in a SRC URI to an external script <script> tag. A returned script may be automatically executed, causing lookup_cb to be called. lookup_cb may iterate over services in a result and may output them into the HTML of the web page http://example.com/index.html.

According to one embodiment, an image 334 may be a HTML tag that incorporates in-line graphics into an HTML document. FIG. 3 may also encompass an <A> tag encapsulating an <IMG> tag where it is described an image 334, thereby allowing a link to take on the appearance of a button, according to one embodiment. With Javascript® a behavior of the image may be scripted to make the button change appearance when a mouse passes over the button or when a user clicks on the button, thereby making the image behave more like a button. For example,

<A HREF=″http://pairing_server.com/f?a=10&b=bar″><IMG SRC=”f.jpg”>call f</IMG></A>

FIG. 3 may also be applicable to an IMG tag where it is described an image 334 used to communicate a call, according to one embodiment. For example,

<IMG SRC=“http://pairing_server.com/f?a=10&b=bar”>calling f . . . </IMG>

This example may correspond to a call f with arguments a=10 and/or b=bar. The pairing server 200 sees

GET /f?a=10&b=bar HTTP/1.1 Host: ec2-204-236-247-87.compute-1.amazonaws.com:7878 Connection: keep-alive Referer: http://dave.flingo.org/browser_behavior_tests/img_link.html Cache-Control: max-age=0 Accept: */* User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3 Accept-Encoding: gzip,deflate Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

A browser may expect an image to be returned by this request. As a result, an IMG send message interface may not threaten a calling web page with script injection attacks. However, it may limit what can be returned with an IMG tag. The pairing server 200 may return a valid transparent IMG with width and height set to communicate a pair. Since an IMG body has been loaded into the calling web page, the height and width of the image are immediately available to the calling page using Javascript®, e.g.,

<HTML> <HEAD> ... <script type=″text/Javascript″> function loaded( ) { var im = document.getElementById(″image″) alert( ″image height=″ + im.height + ″ width=” + im.width ); } </script> </HEAD><BODY>... <IMG ID=″image″ SRC=”http://pairing_server.com/f?a=10&b=bar” onload=″loaded( );″></IMG> </BODY> </HTML>

According to one embodiment, a header 336 may be an origin header, a referrer header, and/or any other supplemental data placed at the beginning of a block of data being stored and/or transmitted. FIG. 3 may be applicable to a passing of a URI of a web page that may include a hyperlink along with a GET request in a “referer [sic]” URI header where it is described a header 336 when a user 820 clicks on a hyperlink rendered from an <A> tag. A pairing server 200 can interpret a referer URI as an URI of a web page to be relayed to a sandbox reachable service 114 that can render web pages. For example, the following hyperlink appears in the web page http://example.com/foo.html

<A HREF=http://pairing_server.com/fling> fling this web page </A>

When a user 820 clicks on “fling this page,” the pairing server 200 may read the referer URI (e.g., associated with a client device 100) to determine that the page http://example.com/foo.html should be relayed to the receiving sandbox-reachable services.

FIG. 3 may also encompass interpreting a referer URI dependent on page content where it is described a header 336, according to one embodiment. For example, a web page 302 that may include a video may cause a reference to the video to be passed to a networked device 102. Similarly, a web page 302 that may include an audio may cause a reference to the audio to be passed to a networked device 102.

According to one embodiment, a form 338 may be a HTML tag that allows a web user to enter data that is sent to a server for processing. For example, FIG. 3 may encompass a sandboxed application 112 sending messages to a sandbox reachable service 114 via HTML FORMs where it is described a form 338. The action of a form may direct the messages via the pairing server 200. Assume a web page may reside at http://example.com/index.html and assume a relay infrastructure may run on a server with example domain “pairing server.com.” The video to be relayed may be titled “Waxing Love.”

<form name=“input” action=“http://pairing_server.com/fling” method=“post”> <INPUT TYPE=“HIDDEN” id=“title” name=“title” value=“Waxing Love” /> <INPUT TYPE=“HIDDEN” id=“description” name=“description” value=“An example video.” /> <INPUT TYPE=“HIDDEN” id=“uri” name=“uri” value=“http://example.com/wax.mp4” /> <INPUT TYPE=“SUBMIT” NAME=“submit” VALUE=“fling” /> </form>

A hidden type may populate an HTTP POST. In this example, an URI of a resource may be passed to a pairing server 200. The pairing server 200 may treat the POST as a message to be forwarded to services. In this example, the server may see something like:

POST /fling HTTP/1.1 Host: pairing_server.com Origin: http://example.com/index.html User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-us) AppleWebKit/533.16 (KHTML, like Gecko) Version/5.0 Safari/533.16 Content-Type: application/x-www-form-urlencoded Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain; q=0.8,image/png,*/*;q=0.5 Referer: http://example.com/index.html Accept-Language: en-us Accept-Encoding: gzip, deflate Content-Length: 95 Connection: keep-alive title=Waxing+Love&description=An+example+video.&uri=http%3A%2F%2Fexampl e.com%2Fwax.mp4 &submit=fling

The intended message may be encoded in key-value pairs of a message body. In this case a title, description, and URI and an operation “fling.”

FIG. 4 is an exploded view of the pairing server 200, according to one embodiment. FIG. 4 shows a pairing server 200, a discovery module 400, a discovery algorithm 402, a relay module 404, a relay algorithm 406, a protocols 408, and a database 422.

The discovery module 400 and the relay module 404 communicate with the database 422, and they all exist within the pairing server 200 of FIG. 4. According to one embodiment, a discovery module 400 may be a self-contained component of a pairing server 200 that detects devices and services on a network. According to one embodiment, a relay module 404 may be a self-contained component of a pairing server 200 that transmits data to an intermediate node located between a source and destination that are separated by a distance that prevents direct communications. According to one embodiment, a database 422 may be a structured collection of information.

A networked device 102 may announce a sandbox reachable service 114 to a discovery module 400. When a shared network 202 is determined to be commonly associated with a client device 100 and a networked device 102, a pairing server 200 may receive, store using a processor 108 and a memory 110, and communicate to a client device 100 a global unique identifier 208 and/or an alphanumeric name 210 in an announcement from a networked device 102 along with a hardware address 222 associated with the networked device 102, a public address pair 220 associated with a sandbox reachable service 114 of the networked device 102, and/or a private address pair 212 associated with the sandbox reachable service 114 of the networked device 102. A shared network 202 is determined to be commonly associated with a client device 100 and a networked device 102 when it is presently shared and/or was previously shared by the networked device 102 and the client device 100.

The discovery algorithm 402 exists within the discovery module 400 of FIG. 4. According to one embodiment, a discovery algorithm 402 may be a procedure for detecting devices and services on a network. A service agent module of a networked device 102 may coordinate communications with a discovery module 400 of a security sandbox 104 and/or a pairing server 200. For example, the service agent sits outside a browser or browser-like security sandbox thereby allowing it to listen on a socket. Thus, it can act as a means for services on the same device to discover one another. The service agent may also announce on behalf of service(s) local to that device.

The relay algorithm 406 exists within the relay module 404 of FIG. 4. According to one embodiment, a relay algorithm 406 may be a procedure for transmitting data to an intermediate node located between a source and destination that are separated by a distance that prevents direct communications. A service agent module of a networked device 102 may coordinate communications with a discovery module 400 of a security sandbox 104 and/or a pairing server 200. For example, the service agent sits outside a browser or browser-like security sandbox thereby allowing it to listen on a socket. Thus, it can act as a relay for messages arriving from a shared network 202.

When a client device 100 and a networked device 102 reside on networks that are incommunicable with each other comprising a firewall separation, a different network separation, a physical separation, and/or an unreachable connection separation, a sandboxed application 112 of a security sandbox 104 of the client device 100 and a sandbox reachable service 114 of the networked device 102 may communicate with each other through a relay service employed by a pairing server 200 having a discovery module 400 and a relay module 404 to facilitate a trusted communication (e.g., by guarding a GUID 208, a private IP address 808, and/or a hardware address 222 of a networked device 102 and/or a sandbox reachable service 114 from a sandboxed application 112) between the sandboxed application 112 and the sandbox reachable service 114.

The discovery module 400 and the relay module 404 can also communicate using the protocols 408 of FIG. 4. According to one embodiment, a protocols 408 may be a system of digital message formats and rules for exchanging those messages in and/or between devices sharing a network.

FIG. 5 is an exploded view of the client device 100, according to one embodiment. FIG. 5 shows a client device 100, a discovery module 500, a relay module 504, a discovery algorithm 502, a relay algorithm 506, an extension 518, a sandboxed application 112, a protocols 508, a Bonjour® protocol 510, a Simple Service Discovery Protocol (SSDP) protocol 512, a local service discovery (LSD) uTorrent® protocol 514, a local area network (LAN) based protocol 516, a multicast protocol 519, and an anycast protocol 520.

The extension 518 exists within the client device 100 of FIG. 5. According to one embodiment, an extension 518 may be a program adding the capabilities of a discovery module 500 and/or a relay module 504 to a browser. A client device 100 may extend a security sandbox 104 with a discovery algorithm 502 and a relay algorithm 506 through a discovery module 500 and a relay module 504 added to the security sandbox 104. A client device 100 may also bypass a pairing server 200 having a discovery algorithm 402 and a relay algorithm 406 when establishing a connection between a sandboxed application 112 and a sandbox reachable service 114 when the security is extended with the discovery algorithm 502 and the relay algorithm 506 through the discovery module 500 and the relay module 504 added to a security sandbox 104.

The discovery module 500, the relay module 504, and the sandboxed application 112 exist within the extension 518 of FIG. 5. The discovery module 500 communicates with the relay module 504 of FIG. 5. According to one embodiment, a discovery module 500 may be a self-contained component of a client device 100 that detects devices and services on a network. According to one embodiment, a relay module 504 may be a self-contained component of a client device 100 that transmits data to an intermediate node located between a source and destination that are separated by a distance that prevents direct communications. A networked device 102 may announce a sandbox reachable service 114 to a discovery module 500. A networked device 102 may also automatically instantiate a communication between a sandbox reachable service 114 of the networked device 102 and a client device 100 when a relay module 504 sends a request from a sandboxed application 112 of the client device 100 to the sandbox reachable service 114.

The discovery algorithm 502 exists within the discovery module 500 of FIG. 5. A client device 100 may apply a discovery algorithm 502 of a security sandbox 104 to determine that a networked device 102 having a sandbox reachable service 114 communicates in a shared network 202 common to the client device 100 and the networked device 102.

The relay algorithm 506 exists within the relay module 504 of FIG. 5. A client device 100 may apply a relay algorithm 506 of a security sandbox 104 to establish a connection between a sandboxed application 112 and a sandbox reachable service 114 of a networked device 102. A client device 100 may utilize a WebSocket (e.g., a web technology providing full-duplex communications channels over a single Transmission Control Protocol connection) and/or a long polling service message query interface to reduce a latency of message delivery during a trusted communication between a sandboxed application 112 and a sandbox reachable service 114. A client device 100 may also optimize a polling period between polling such that it is less than a timeout period of a session through the relay service. A client device 100 may initiate a relay service through a series of web pages where information is communicated using a hyperlink 328 that points at a pairing server 200, and/or a form 338 having a confirmation dialog that is submitted back to the pairing server 200. A global unique identifier 208 (e.g., of a sandbox reachable service 114) may be masked through a pairing server 200 when a confirmation dialog is served from the pairing server 200.

The discovery algorithm 502 and the relay algorithm 506 can communicate using the protocols 508 of FIG. 5. The Bonjour® protocol 510, the SSDP protocol 512, the LSD uTorrent® protocol 514, the LAN-based protocol 516, the multicast protocol 519, and the anycast protocol 520 exist within the protocols 508 of FIG. 5. According to one embodiment, a Bonjour® protocol 510 may be a system of technologies including service discovery, address assignment, and hostname resolution developed by Apple®. According to one embodiment, a SSDP protocol 512 may be a network protocol based on the Internet Protocol Suite for advertisement and discovery of network services and presence information that is accomplished without assistance of server-based configuration mechanisms and without special static configuration of a network host. According to one embodiment, a LSD uTorrent® protocol 514 may be an extension to the BitTorrent® file distribution system that is designed to support the discovery of local BitTorrent® peers, aiming to minimize traffic through an Internet service provider's (ISP) channel and minimize use of higher-bandwidth LAN while implemented in a client with a small memory footprint. According to one embodiment, a LAN-based protocol 516 may be a system of broadcast-based local area network discovery. According to one embodiment, a multicast protocol 519 may be a system of delivering information simultaneously to a group of destination devices in a single transmission from a source. According to one embodiment, an anycast protocol 520 may be a system of routing datagrams from a single sender to the topologically nearest node in a group of potential receivers, though it may be sent to several nodes, all identified by the same destination address.

A discovery algorithm 502 may utilize a protocols 508 comprising a Bonjour® protocol 510, a SSDP protocol 512, a LSD uTorrent® protocol 514, a multicast protocol 519, an anycast protocol 520, and/or another LAN-based protocol 516 that discovers services in a LAN based on a broadcast from any one of an operating system service, a security sandbox 104, a client device 100, a sandbox reachable service 114, and a networked device 102.

FIG. 6 is a table of example network information stored in a database 422 of a pairing server 200, according to one embodiment. FIG. 6 shows a GUID 208, an alphanumeric name 210, a network 600, a service 601, a Network Address Translator (NAT) 602, a port number 604, an IP address 606, and a table 650. The GUID 208, the alphanumeric name 210, the network 600, the service 601, the NAT 602, the port number 604, and the IP address 606 are headings for each column of a table 650 of FIG. 6.

According to one embodiment, a network 600 may be a collection of hardware interconnected by communication channels that allow sharing of resources and information. According to one embodiment, a service 601 may be a description and/or a name of a service provided by a device. According to one embodiment, a NAT 602 may be an indication of whether or not a NAT device is present on a network 600. According to one embodiment, a port number 604 may be a 16-bit reference number for a process-specific software construct serving as a communications endpoint in a computer's host operating system. According to one embodiment, an IP address 606 may be a numerical label assigned to each device participating in a computer network that uses the Internet Protocol for communication. According to one embodiment, a table 650 may be a set of data elements that is organized using a model of vertical columns which are identified by names and horizontal rows. A sandbox reachable service 114 may communicate a GUID 208 and/or an alphanumeric name 210 to a pairing server 200 along with an IP address 606 and/or a port number 604 of the sandbox reachable service 114.

FIG. 7 is a block diagram of a method by which a security sandbox 104 can communicate with a sandbox reachable service 114 that previously operated on a shared network 202, according to one embodiment. FIG. 7 shows a client device 100, a storage 109, a remote access token 702, a private IP address 704, and a hardware address 222. The storage 109 exists within the client device 100 of FIG. 7. The remote access token 702 exists within the storage 109 of FIG. 7. According to one embodiment, a remote access token 702 may be an object encapsulating a security descriptor of a process so that a client device 100 and a networked device 102 that previously established a communication session automatically recognize each other. A cookie associated with a security sandbox 104 may be used to store a remote access token 702 on a storage 109 (e.g., Web storage, HTML5 storage) of a client device 100. A client device 100 can communicate with a sandbox reachable service 114 that previously operated on a common shared network 202 through a remote access token 702.

The private IP address 704 and the hardware address 222 comprise aspects of the remote access token 702 of FIG. 7. According to one embodiment, a private IP address 704 may be an IP address of a node on a private network that may not be used to route packets on the public Internet. A remote access token 702 may identify a set of communicable private Internet Protocol (IP) address (e.g., the private ip address 704) and/or hardware addresses (e.g., the hardware address 222) associated with a sandbox reachable service 114 that previously operated on a common shared network 202 with a client device 100. For example, FIG. 7 may encompass a preference for associating a device with a hardware address 222 where it is described a hardware address 222. A private IP address 704 may change as devices move between networks. However, a hardware address 222 may be a stable, long-term pseudonym for a device and thus may serve a good value from which to derive a remote access token 702.

FIG. 8 is a schematic diagram of a private network 800 and a private network 802 communicating over the public Internet via a NAT device 804 and a NAT device 806, according to one embodiment. FIG. 8 shows a client device 100, a networked device 102, a pairing server 200, a private network 800, a private network 802, a NAT device 804, a NAT device 806, a private IP address 808, a private IP address 810, a public IP address 812, a public IP address 814, a tablet device 816, a printer 818, and a user 820.

The private network 800 and the private network 802 communicate bidirectionally through the pairing server 200 of FIG. 8. According to one embodiment, a private network 800 may be a home network and/or any other network with private IP space that may be behind a NAT device 804. According to one embodiment, a private network 802 may be an office network and/or any other network with private IP space that may be behind a NAT device 806. A client device 100 (e.g., laptop) and a networked device 102 (e.g., television) may reside on networks that are incommunicable with each other comprising a firewall separation, a different network separation, a physical separation, and/or an unreachable connection separation. A sandboxed application 112 of a security sandbox 104 of the client device 100 and a sandbox reachable service 114 of the networked device 102 may communicate with each other through a relay service employed by a pairing server 200 having the discovery module and the relay module to facilitate a trusted communication between the sandboxed application 112 and the sandbox reachable service 114.

The NAT device 804, the networked device 102, and the tablet device 816 are all interconnected and exist within the private network 800 of FIG. 8. According to one embodiment, a NAT device 804 may be a device for modifying IP address information in IP packet headers while in transit across a traffic routing device. According to one embodiment, a tablet device 816 may be a one-piece mobile computer, primarily operated by touchscreen and/or an onscreen virtual keyboard. A NAT device 804 may be coupled with a network on which a networked device 102 operates.

The NAT device 806, the client device 100, and the printer 818 are all interconnected and exist within the private network 802 of FIG. 8. According to one embodiment, a NAT device 806 may be a device for modifying IP address information in IP packet headers while in transit across a traffic routing device. According to one embodiment, a printer 818 may be a peripheral device which produces a representation of an electronic document on physical media. A NAT device 806 may be coupled with a network on which a client device 100 operates.

The NAT device 804 connects to the pairing server 200 through the public IP address 812 of FIG. 8. The NAT device 804 connects to the networked device 102 through the private IP address 808 of the networked device 102 of FIG. 8. According to one embodiment, a public IP address 812 may be an IP address of a private network 800 that may be used to route packets on the public Internet. According to one embodiment, a private IP address 808 may be an IP address of a networked device 102 on a private network 800. A trusted communication may be facilitated in a manner such that a sandboxed application 112 never learns a private IP address 808 and/or a hardware address 222 of a networked device 102 when a NAT device 804 may translate a private IP address 808 of a networked device 102 to a public IP address 812 visible to a sandboxed application 112.

The NAT device 806 connects to the pairing server 200 through the public IP address 814 of FIG. 8. The NAT device 806 connects to the client device 100 through the private IP address 810 of the client device 100 of FIG. 8. According to one embodiment, a public IP address 814 may be an IP address of a private network 802 that may be used to route packets on the public Internet. According to one embodiment, a private IP address 810 may be an IP address of a networked device 102 on a private network 802. A trusted communication may be facilitated in a manner such that a sandboxed application 112 never learns a private IP address 808 and/or a hardware address 222 of a networked device 102 when a NAT device 806 may receive communications from a public IP address 812 of a private network 800 on which a sandbox reachable service 114 operates.

For example, FIG. 8 may encompass a sandboxed application 112 being constrained to know nothing but a description and/or name of a service (e.g., no private IP address 808, no hardware address 222, no GUID 208) where it is described a private IP address 808.

FIG. 8 may also be applicable to a sandboxed application 112 being constrained to know nothing at all about who receives a communication (e.g., no private IP address 808, no hardware address 222, no GUID 208, no description and/or name of a service) where it is described a private IP address 808, according to one embodiment. For example, a sandboxed application 112 may include a hyperlink 328 to a pairing server 200 in which the hyperlink 328 may specify a message but no recipient http://flingo.tv/fling/a?url=url of media to be played. A pairing server 200 may disambiguate an intended recipient (e.g., by returning a form 338 to a user 820 in which the user 820 may select a sandbox reachable service 114). A returned form 338 may execute in a security sandbox 104 associated with a domain of a pairing server 200 which may be different from a security sandbox 104 of a sandboxed application 112.

The user 820 exists within the private network 802 of FIG. 8. According to one embodiment, a user 820 may be a human and/or software agent who uses a computer and/or network service.

In another aspect, a method of a client device includes constraining an executable environment in a security sandbox. The method also includes executing a sandboxed application in the executable environment using a processor and a memory. Further, the method includes automatically instantiating a connection between the sandboxed application and a sandbox reachable service of a networked media device.

The method may include processing an identification data associated with the sandbox reachable service sharing a public address with the client device. The method may also include determining a private address pair of the sandbox reachable service based on the identification data. Additionally, the method may include establishing a communication session between the sandboxed application and the sandbox reachable service using a cross-site scripting technique of the security sandbox. Further, the method may include appending a header of a hypertext transfer protocol to permit the networked media device to communicate with the sandboxed application as a permitted origin domain through a Cross-origin resource sharing (CORS) algorithm. The header may be either one of a origin header when the CORS algorithm is applied and a referrer header in an alternate algorithm.

The method may further include accessing a pairing server when processing the identification data associated with the sandbox reachable service sharing the public address with the client device. The pairing server may perform a discovery lookup of any device that has announced that it shares the public address associated with the client device. The sandbox reachable service may announce itself to the pairing server prior to the establishment of the communication session between the sandboxed application and the sandbox reachable service. The sandbox reachable service may also announce its availability across a range of public addresses such that the sandboxed application communicates with the sandbox reachable service in any one of the range of the public addresses. However, the range of public addresses may be known by the pairing server so that the announcement of the availability of the sandbox reachable service across the range of public addresses is unnecessary. The sandbox reachable service may communicate a global unique identifier and/or an alphanumeric name to the pairing server along with the private address pair of the sandbox reachable service. The private address pair may include a private IP address and a port number associated with the sandbox reachable service.

The method may further include eliminating a communication through a centralized infrastructure when the sandboxed application and the sandbox reachable service communicate in a shared network common to the client device and the networked media device when the connection is established. The shared network may be a local area network, a multicast network, an anycast network, and/or a multilan network. The method may also include minimizing a latency in the communication session when the sandboxed application and the sandbox reachable service communicate in the shared network common to the client device and the networked media device when the connection is established. Further, the method may include improving privacy in the communication session when the sandboxed application and the sandbox reachable service communicate in the shared network common to the client device and the networked media device when the connection is established.

The sandboxed application may be a web page, a script, a binary executable, an intermediate bytecode, an abstract syntax tree, and/or an executable application in the security sandbox. The sandboxed application may comprise a markup language application such as a HyperText Markup Language 5 (HTML5) application, a Javascript® application, an Adobe® Flash® application, a Microsoft® Silverlight® application, a JQuery® application, and/or an Asynchronous Javascript® and a XML (AJAX) application. An access control algorithm may govern a policy through which a secondary authentication is required when establishing a communication between the sandboxed application and the networked media device. The method may include utilizing an exception to a same origin policy through a use of a hyperlink, a form, the script, a frame, a header, and an image when establishing the connection between the sandboxed application and the sandbox reachable service.

The method may include extending the security sandbox with a discovery algorithm and a relay algorithm through a discovery module and a relay module added to the security sandbox. The method may also include bypassing a pairing server having the discovery algorithm and the relay algorithm when establishing the connection between the sandboxed application and the sandbox reachable service when the security sandbox is extended with the discovery algorithm and the relay algorithm through the discovery module and the relay module added to the security sandbox.

The method may further include applying the discovery algorithm of the security sandbox to determine that the networked media device having the sandbox reachable service communicates in a shared network common to the client device and the networked media device. The method may also include applying the relay algorithm of the security sandbox to establish the connection between the sandboxed application and the sandbox reachable service of the networked media device. The discovery algorithm may utilize a protocol comprising a Bonjour® protocol, a SSDP protocol, a LSD uTorrent® protocol, a multicast protocol, an anycast protocol, and/or another Local Area Network (LAN) based protocol that discovers services in a LAN based on a broadcast from any one of an operating system service, the security sandbox, the client device, the sandbox reachable service, and the networked media device.

A cookie associated with the security sandbox may be used to store a remote access token on a storage of the client device. The remote access token may identify a set of communicable private Internet Protocol (IP) addresses and/or hardware addresses associated with sandbox reachable services that previously operated on a common shared network with the client device. The client device may communicate with the sandbox reachable services that previously operated on the common shared network through the remote access token.

The client device and the networked media device may reside on networks that are incommunicable with each other comprising a firewall separation, a different network separation, a physical separation, and/or an unreachable connection separation. The sandboxed application of the security sandbox of the client device and the sandbox reachable service of the networked media device may communicate with each other through a relay service employed by a pairing server having a discovery module and a relay module to facilitate a trusted communication between the sandboxed application and the sandbox reachable service.

The trusted communication may be facilitated in a manner such that the sandboxed application never learns a private IP address and/or a hardware address of the networked media device. This may occur when a first Network Address Translator (NAT) device receives communications from a public IP address of a different network on which the sandbox reachable service operates, and a second NAT device translates the private IP address of the networked media device to the public IP address visible to the sandboxed application. The first NAT device may be coupled with a network on which the client device operates. The second NAT device may be coupled with the different network on which the networked media device operates.

The networked media device may comprise a number of sandbox reachable applications including the sandbox reachable application. A service agent module of the networked media device may coordinate communications with the discovery module of the security sandbox and/or the pairing server. The security sandbox may be an operating system on which the sandboxed application is hosted and/or a browser application of the operating system. The networked media device may be a television, a projection screen, a multimedia display, a touchscreen display, an audio device, and/or a multidimensional visual presentation device.

The method may include utilizing a WebSocket and/or a long polling service message query interface to reduce a latency of message delivery during the trusted communication between the sandboxed application and the sandbox reachable service. The method may also include optimizing a polling period between polling such that it is less than a timeout period of a session through the relay service. The method may further include initiating the relay service through a series of web pages where information is communicated using hyperlinks that point at the pairing server, and/or a form having a confirmation dialog that is submitted back to the pairing server. A global unique identifier may be masked through the pairing server when the confirmation dialog is served from the pairing server.

In one embodiment, a method of a networked device includes announcing a sandbox reachable service of the networked device to a discovery module using a processor and memory. The method also includes automatically instantiating a communication between the sandbox reachable service of the networked device and a client device when a relay module sends a request from a sandboxed application of the client device to the sandbox reachable service.

In yet another embodiment, a system includes a networked device to announce a sandbox reachable service of the networked device to a discovery module using a processor and memory. The system also includes a client device to constrain an executable environment in a security sandbox, to execute a sandboxed application in the security sandbox, and to automatically instantiate a connection between the sandboxed application and the sandbox reachable service of the networked device.

In still another embodiment, a method of a pairing server includes receiving, storing using a processor and a memory, and communicating to a client device a global unique identifier and/or an alphanumeric name in an announcement from a networked device along with a hardware address associated with the networked device, a public address pair associated with a sandbox reachable service of the networked device, and/or a private address pair associated with the sandbox reachable service of the networked device when a shared network is determined to be commonly associated with the client device and the networked device. The shared network is a local area network, a multicast network, an anycast network, and/or a multilan network.

For example, Jane may watch a movie and/or access an application through her mobile device while sitting on a couch in her living room. Jane may wish to automatically display the movie and/or application of a big screen television in front of her couch. Jane may use a gesture to transport the movie and/or application to the big screen television. For example, Jane may ‘fling’ (or flick) the screen on her mobile device in which the movie and/or application is running in an upward motion, and instantly transport the movie and/or application onto her big screen television. In an alternate embodiment, the big screen television may automatically detect that Jane is playing the movie and/or running the application on her mobile device and automatically launch the movie (in its current play state) and/or run the application on the big screen television after detection (without requiring a fling or flick haptic gesture by Jane).

While Jane is playing the movie and/or running the application on the big screen television, Jane may see advertisements that relate to exactly what she is currently watching on the big screen television on her mobile device through the capture infrastructure described herein. Conversely, if Jane were playing the movie and/or running the application on her mobile device, she could see advertisements directly related to the activities she is currently doing on her big screen television (and or simultaneously on the mobile device). This is made possible through the various methods and techniques described herein, particularly with respect to a centralized capture infrastructure that annotates an audio-visual stream with meta-data.

It is obvious to one skilled in the art that capture infrastructure 105 discussed above may include a memory (e.g., a volatile and/or a non-volatile memory) communicatively coupled to a processor. Said processor may be configured to execute instructions related to the operations discussed above with respect to capture infrastructure 105. To generalize, in one or more embodiments, capture infrastructure 105 may determine content identifier 111 by applying an automatic content recognition algorithm (e.g., a first automatic content recognition algorithm from algorithm library 107) to fingerprint data of an audio-visual data rendered on a networked media device (e.g., networked device 102).

In one or more embodiments, capture infrastructure 105 may then associate the content identifier with additional data (discussed above as advertisement data, audio identifier determined by applying another (e.g., a second) automatic content recognition algorithm from algorithm library 107 to fingerprint data of audio data received by capture infrastructure 105 for a same content identified by content identifier 111, a text identifier determined by applying an optical character recognition algorithm from algorithm library 107 discussed above, with the text identifier identifying a brand, a product, a person, and/or a location shown in the same content, or a logo name discussed above) derived from information other than the fingerprint data.

It should be noted that the example audio identifier may identify a piece of music in the same content discussed above, and/or identify a person speaking therein. Further, in one or more embodiments, the determination of the example text identifier discussed above may involve applying the optical character recognition algorithm to audio-visual data received by capture infrastructure 105 for a same content identified by content identifier 111 and by comparing recognized text to entries in master database 109. All reasonable variations are within the scope of the exemplary embodiments discussed herein.

Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments. For example, the various devices and modules described herein may be enabled and operated using hardware circuitry (e.g., CMOS based logic circuitry), firmware, software or any combination of hardware, firmware, and/or software (e.g., embodied in a machine readable medium). For example, the various electrical structures and methods may be embodied using transistors, logic gates, and/or electrical circuits (e.g., application specific integrated (ASIC) circuitry and/or Digital Signal Processor (DSP) circuitry).

In addition, it will be appreciated that the various operations, processes, and/or methods disclosed herein may be embodied in a machine-readable medium and/or a machine accessible medium compatible with a data processing system (e.g., a computer device; capture infrastructure 105). Accordingly, the specification and drawings are to be regarded in an illustrative in rather than a restrictive sense. 

What is claimed is:
 1. A method of a capture infrastructure comprising: dividing an audio-visual data rendered on a networked media device into a series of scenes, said networked media device comprising a sandbox reachable service; applying an automatic content recognition algorithm to a first scene of the series of scenes to determine a content identifier; associating an advertisement data with the determined content identifier; identifying a correlation pattern between the first scene and a second scene of the series of scenes; associating the advertisement data to the second scene of the series of scenes; and identifying targeted content to be targeted to a client device associated with the networked media device, said client device supporting sandboxed application execution.
 2. The method of claim 1, further comprising associating, with the content identifier, an audio identifier determined from fingerprint data of audio data received by the capture infrastructure for a same content identified by the content identifier.
 3. The method of claim 2, comprising the audio identifier identifying a piece of music in the same content.
 4. The method of claim 2, comprising the audio identifier identifying a person speaking in the same content.
 5. The method of claim 1, further comprising associating, with the content identifier, a text identifier determined by applying an optical character recognition algorithm to data received by the capture infrastructure for a same content identified by the content identifier and by comparing recognized text to entries in a master database, wherein the text identifier identifies at least one of: a brand, a product, a person, and a location shown in the same content.
 6. The method of claim 5, comprising the additional data text identifier being a logo name determined by comparing the entries in the master database with a logo data of the audio-visual data identified using a logo detection algorithm.
 7. The method of claim 1, comprising the association of the advertisement data with the content identifier being based on a correlation between a metadata of the advertisement data provided by a content provider and the content identifier.
 8. The method of claim 1, further comprising at least one of: automatically dividing the audio-visual data into the series of scenes based on a semantic grouping of actions in the audio-visual data: analyzing the audio-visual data in advance of a broadcast to determine content identifiers associated with each commercial in the audio-visual data such that advertisements are pre-inserted into the audio-visual data prior to the broadcast; and applying a time-order algorithm to automatically match the advertisement data to the audio-visual data when the correlation pattern is identified.
 9. The method of claim 1, further comprising causing rendering of the identified targeted content in the sandboxed application executing within the client device.
 10. A capture infrastructure, comprising: a memory; and a processor communicatively coupled to the memory, the processor configured to execute instructions to: divide an audio-visual data rendered on a networked media device into a series of scenes, said networked media device comprising a sandbox reachable service, apply an automatic content recognition algorithm to a first scene of the series of scenes to determine a content identifier, associate an advertisement data with the determined content identifier, identify a correlation pattern between the first scene and a second scene of the series of scenes, associate the advertisement data to the second scene of the series of scenes, and identifying targeted content to be targeted to a client device associated with the networked media device, said client device supporting sandboxed application execution.
 11. The capture infrastructure of claim 10, wherein the processor is further configured to execute instructions to associate, with the content identifier, an audio identifier determined from fingerprint data of audio data received by the capture infrastructure for a same content identified by the content identifier.
 12. The capture infrastructure of claim 11, wherein the audio identifier identifies a piece of music in the same content.
 13. The capture infrastructure of claim 11, wherein the audio identifier identifies a person speaking in the same content.
 14. The capture infrastructure of claim 10, wherein the processor is further configured to execute instructions to associate, with the content identifier, a text identifier determined by applying an optical character recognition algorithm to data received by the capture infrastructure for a same content identified by the content identifier and by comparing recognized text to entries in a master database, wherein the text identifier identifies at least one of: a brand, a product, a person, and a location shown in the same content.
 15. The capture infrastructure of claim 14, wherein the text identifier is a logo name determined by comparing the entries in the master database with a logo data of the audio-visual data identified using a logo detection algorithm.
 16. The capture infrastructure of claim 10, wherein the processor is configured to execute instructions to associate the advertisement data with the content identifier based on a correlation between a metadata of the advertisement data provided by a content provider and the content identifier.
 17. The capture infrastructure of claim 10, wherein the processor is further configured to execute instructions to at least one of: automatically divide the audio-visual data into the series of scenes based on a semantic grouping of actions in the audio-visual data, analyze the audio-visual data in advance of a broadcast to determine content identifiers associated with each commercial in the audio-visual data such that advertisements are pre-inserted into the audio-visual data prior to the broadcast, and apply a time-order algorithm to automatically match the advertisement data to the audio-visual data when the correlation pattern is identified. 